• Resolve builtin elements from namespace-imported styled-components
  - Record ImportNamespaceSpecifier bindings for namespace imports
  - Handle JSXMemberExpression references (e.g. <Styled.Section>)
  - Follow namespace imports to resolve underlying HTML elements
• Replace per-file git operations with streaming git archive
  - Eliminate thousands of process spawns and disk round-trips
  - Reduce diff snapshot time from ~2 min to ~6 s on large repositories

Add test for namespace-imported styled-components

e2e/react.test.ts

Record ImportNamespaceSpecifier bindings

src/analyzers/react/bindings.ts

Replace git cat-file with streaming git archive

src/analyzers/react/diff.ts

Description

materializeGitTreeSnapshot now invokes sh -c 'git ... | tar ...', which will fail on systems
without a POSIX shell (commonly Windows) and makes foresthouse react --diff unusable there.

Code

src/analyzers/react/diff.ts[R993-1005]

+  const result = spawnSync(
+    'sh',
+    [
+      '-c',
+      'git -C "$0" archive "$1" | tar -xf - -C "$2"',
    repositoryRoot,
-      ['cat-file', '-p', `${tree}:${filePath}`],
-      {
-        trim: false,
-      },
-    )
-    const absolutePath = path.join(snapshotRoot, ...filePath.split('/'))
-
-    fs.writeFileSync(absolutePath, fileContent)
-  })
-
-  return snapshotRoot
-}
-
-function ensureSnapshotDirectory(snapshotRoot: string, filePath: string): void {
-  const parentDirectory = path.dirname(filePath)
+      tree,
+      snapshotRoot,
+    ],
+    {
+      stdio: ['ignore', 'pipe', 'pipe'],
+    },
+  )

Evidence

The snapshot extraction is executed via spawnSync('sh', ['-c', ...]), so the feature depends on
sh being present in PATH. The README positions this as a Node.js CLI and documents `foresthouse
react --diff` without stating Unix-only prerequisites.

src/analyzers/react/diff.ts[985-1005]
README.md[8-34]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`materializeGitTreeSnapshot()` currently shells out via `sh -c` to run a pipeline (`git archive | tar`). This breaks on environments without a POSIX shell (notably many Windows installs), causing `foresthouse react --diff` to fail immediately.
## Issue Context
The tool is a Node.js CLI and the README advertises `foresthouse react --diff` without platform constraints; relying on `sh` is a new, undocumented runtime requirement.
## Fix Focus Areas
- src/analyzers/react/diff.ts[985-1015]
## Suggested fix approach
- Avoid `sh -c` entirely.
- Prefer one of:
- **Two-process pipeline without a shell**: spawn `git` and `tar` directly (e.g., `spawn('git', ['-C', repo, 'archive', tree])` piped to `spawn('tar', ['-xf', '-', '-C', snapshotRoot])`), handling exit codes for both.
- **Portable fallback**: if `process.platform === 'win32'` or `tar` is unavailable, fall back to the prior per-file `git cat-file` materialization method.
- If you keep `tar`, consider checking for command availability up front and emitting a clear error explaining prerequisites.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

On snapshot extraction failure with empty stderr, the thrown error message can become blank because
?? treats empty string as a valid value, hiding the actual failure cause.

Code

src/analyzers/react/diff.ts[R1007-1011]

+  if (result.error !== undefined || result.status !== 0) {
+    fs.rmSync(snapshotRoot, { recursive: true, force: true })
+    throw new Error(
+      `Failed to extract Git tree snapshot: ${result.stderr?.toString('utf8').trim() ?? result.error?.message ?? 'Unknown error'}`,
+    )

Evidence

The error message uses result.stderr?.toString('utf8').trim() ?? ...; if stderr is an empty
string, it is not nullish so the fallback to result.error?.message / Unknown error won’t run,
producing Failed to extract Git tree snapshot:  with no details.

src/analyzers/react/diff.ts[1007-1011]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`materializeGitTreeSnapshot()` can throw an error with an empty/blank reason when the subprocess exits non-zero but writes nothing to stderr.
## Issue Context
The error string is built using nullish coalescing (`??`) on a potentially empty trimmed stderr string; empty string is not nullish, so the fallback message is skipped.
## Fix Focus Areas
- src/analyzers/react/diff.ts[1007-1011]
## Suggested fix approach
- Compute stderr as a trimmed string and only use it if it’s non-empty.
- Include additional context such as `status`/`signal`.
Example direction (not exact code):
- `const stderr = Buffer.isBuffer(result.stderr) ? result.stderr.toString('utf8').trim() : String(result.stderr ?? '').trim()`
- `const details = stderr.length > 0 ? stderr : result.error?.message ?? `exit ${result.status ?? 'unknown'}``
- Throw with `details`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.